Gail Shaw wrote:

> >I've noticed this happening for a while..just not mentioned it. I'm sure it
> never used to
> >happen. Someone please confirm my sanity.
> >
> 
> I'll confirm it. I had the same problem. I was doing a quick scene with
> multiple
> reflective spheres over multiple checkered squares. All were  fine til I
> added
> a checkered square (red/blue). That plane rendered green and blue. I played
> with it for  a few days then left it. (Was pov 3.0 for win 95).
> Gail

  The reason you people are seeing this now and perhaps not on
older versions of Pov is because unknown to you the Pov team has
silently been working in the back ground to fix annoying little
things the program does like stopping to inform a user that they
are stupid and misplaced a comma.
  More specificaly they have started assigning a default pigment
colors to patterns that none specified by you. This helps because
if you forget to specify a color for the pattern Pov will render
the scene with the default color instead of stopping to issue a
warning message suggesting you fix your work before you try again.
  It manifests it's self when you improperly specify color list
patterns like the missing comma seperator in the example today.
It is mentioned in the docs in several catagories concerning
list patterns that a comma seperator is needed or unexpected
results can be expected.

 If you want to see ugly attach a bozo pigment pattern to an object
and leave the color specification empty.

 The three color list pattern types that the comma seperators are
required for are the Brick, Checker, and Hexagon patterns.



-- 
Ken Tyler

mailto://tylereng@pacbell.net

Post a reply to this message